Skip to content

feat: improve blazemeter-administration skill score (82% → 93%)#77

Draft
yogesh-tessl wants to merge 1 commit into
Blazemeter:mainfrom
yogesh-tessl:improve/skill-review-optimization
Draft

feat: improve blazemeter-administration skill score (82% → 93%)#77
yogesh-tessl wants to merge 1 commit into
Blazemeter:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl

@yogesh-tessl yogesh-tessl commented May 18, 2026

Copy link
Copy Markdown

Hey @Baraujo25 👋

truly impressive work. 15 skills that map the entire BlazeMeter platform, from getting started guides through performance testing, API monitoring, service virtualisation, and scripting. The troubleshooting skill alongside the detailed private locations and network security skills shows you're covering the real-world complexity that teams actually hit when running load tests at scale.

ran your skills through tessl skill review at work and found some targeted improvements for blazemeter-administration. Here's the before/after:

Skill Before After Change
blazemeter-administration 82% 93% +11%

the other 14 skills were already solid, baselines ranged from 70% to 82% across the board. I focused on blazemeter-administration since it's the account-level entry point and had the clearest path to improvement.

Changes made

Content improvements (biggest impact):

  • MCP tools table: Replaced verbose bullet-list of tools with a compact reference table showing tool name, action, required args, and purpose - easier to scan and copy-paste
  • Concrete invocation examples: Added actual argument formats (e.g., {"account_id": 12345}) to example workflows so they're copy-paste ready
  • Validation checkpoints: Added verification steps to workflows - check for valid account IDs before proceeding, verify responses have no error field, handle AI consent errors gracefully
  • New workflow: Added "Listing Available Test Locations" example showing read_locations with purpose filtering
  • Removed redundancy: Eliminated the duplicate "When to Use Each Reference" section (was restating the Reference Files descriptions) and the generic "Overview" section
  • Flattened references: Collapsed per-reference sub-headers into a single clean list with richer inline descriptions (e.g., added "RBAC and bucket management" to API Monitoring Teams)

Unchanged:

  • Description (already scoring 100%) - left untouched
  • All reference files - no changes to the 7 reference documents

also stress-tested your blazemeter-administration skill against a few real-world task evals and it held up really well on multi-workspace account discovery with AI consent validation chains. Kudos for that.

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

If you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

Hey @Baraujo25 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements for `blazemeter-administration`. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| blazemeter-administration | 82% | 93% | +11% |

The other 14 skills were already solid — baselines ranged from 70% to 82% across the board. I focused on `blazemeter-administration` since it's the account-level entry point and had the clearest path to improvement.

Changes made:

- MCP tools table: Replaced verbose bullet-list of tools with a compact reference table showing tool name, action, required args, and purpose
- Concrete invocation examples: Added actual argument formats (e.g., {"account_id": 12345}) to example workflows so they're copy-paste ready
- Validation checkpoints: Added verification steps to workflows — check for valid account IDs before proceeding, verify responses have no error field, handle AI consent errors gracefully
- New workflow: Added "Listing Available Test Locations" example showing read_locations with purpose filtering
- Removed redundancy: Eliminated the duplicate "When to Use Each Reference" section and the generic "Overview" section
- Flattened references: Collapsed per-reference sub-headers into a single clean list with richer inline descriptions

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch — just saw room for improvement and wanted to contribute.
@yogesh-tessl

Copy link
Copy Markdown
Author

hey @Baraujo25, just checking in on this one, happy to make any changes if something needs tweaking!
Take your time, totally understand if reviews follow a cadence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant